Skip to content

Bug: localscore seems only use half of the cpu threads #739

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
fengwang opened this issue Apr 6, 2025 · 1 comment
Open

Bug: localscore seems only use half of the cpu threads #739

fengwang opened this issue Apr 6, 2025 · 1 comment

Comments

@fengwang
Copy link

fengwang commented Apr 6, 2025

Contact Details

No response

What happened?

I tested localscore on my home server, the test result is at https://www.localscore.ai/result/417.
This server has two E5-2699 v3 CPUs installed, but I noticed only first half of the available threads are utilized, as is shown in the attached htop resource monitor screenshot.

Image

Version

llamafile v0.9.2

What operating system are you seeing the problem on?

Linux

Relevant log output

see to https://www.localscore.ai/result/417
@cjpais
Copy link
Collaborator

cjpais commented Apr 7, 2025

I will take a look at this soon, I think there might be some code which is used to determine the threads, and it might be avoiding hyperthreading or similar

Mainly would want to check if it improves or reduces performance.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants